[tidy] Fix JavaScript formatting in Copilot log parsing files #2056
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Fixed trailing whitespace and indentation in parse_copilot_log.cjs - Fixed formatting in parse_copilot_log.test.cjs - All files now comply with Prettier formatting rules
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixed JavaScript formatting issues found by Prettier in Copilot log parsing files.
Changes Made
Verification
✅ All formatting checks pass (
make lint)✅ All tests pass (
make test)✅ Workflows recompiled successfully (
make recompile)Details
These files had inconsistent whitespace and indentation that didn't comply with the Prettier configuration. The changes are purely cosmetic - no functional changes were made to the code.
All changes align with the project's code quality standards.